home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #15
/
Monster Media Number 15 (Monster Media)(July 1996).ISO
/
bbs_misc
/
mag9demo.zip
/
SES_DIR.ZIP
/
QWK.MAP
< prev
next >
Wrap
Text File
|
1996-04-01
|
5KB
|
113 lines
;
; This file should be placed in your SESSION DIRectory!!
;
; The format of this file is:
;
; BBSID: SOMENET
; old=new old=new old=new
;
; BBSID: OTHERNET
; old=new old=new old=new
;
; BBSID: THIRDNET
; old=new old=new old=new old=new old=new
; old=new old=new old=new old=new old=new
; old=new old=new old=new
;
;
; Note that Magnum uses base:conf (ie: msgbase 2, conference E) which
; is identical to the following conference numbers:
;
; MsgBase 0 (A-Z) = 0-25
; MsgBase 1 (A-Z) = 26-51
; MsgBase 2 (A-Z) = 52-77
; MsgBase 3 (A-Z) = 78-103
; .
; .
; .
; MsgBase 255 (A-Z) = 6630-6655
;
; -- This is a partial listing; for a full listing, refer to
; the file CONF_NUM.TXT for easy lookup of conference numbers.
; You'll need to know conference numbers for other systems
; wishing to exchange mail with you!
;
; If you're not using the 'extended msgbase module', then your system
; only has msgbase 0 (A-Z) which translates to conference areas 0-25.
;
;
; Format of old=new (ie: if packet contains conference areas 100-109,
; and you wish to map it to your 26-35 which
; is msgbase 2, conferences a-j, your map might
; look like this):
;
; 100=26 101=27 102=28 103=29 104=30
; 105=31 106=32 107=33 108=34 109=35
;
; or like this:
;
; 100=2:A 101=2:B 102=2:C 103=2:D 104=2:E
; 105=2:F 106=2:G 107=2:H 108=2:I 109=2:J
;
; Note that there may be conferences in which you did not expect, for
; this situation, you can assign a default for all unmapped conferences
; by following the BBS ID with the default conference. Example:
;
; BBSID: SOMENET 32
;
; or
;
; BBSID: SOMENET 2:G
;
;
; Lines starting with a semicolon character are comment lines and
; are ignored. Blank lines are also ignored.
;
; As many BBSID's and old=new statements as you need are accomodated.
; No single text line may exceed 80 characters.
;
; As for the RJEQWK.EXE program, the program will read this file under
; the following circumstances:
;
; - BBSID within the .MSG packet of the .REP file does not match the
; BBSID of your system - processing will continue if a matching BBSID
; is found in this file (3rd command-line parm to RJEQWK.EXE required).
;
; - If the optional 3rd command-line argument specifies a BBSID, the
; program will first attempt to open up the .REP file that matches
; your system's BBSID, if not found (in the work directory), it will
; then attempt to open the .REP file matching the BBSID specified in
; the command-line parm. The command-line parm will also look for
; the matching BBSID entry in this file for mapping.
;
; NOTE: If a matching BBSID is not found in this file, RJEQWK.EXE will
; attempt a one-on-one mapping (ie: conference numbers of the
; incoming packet will match identically to the same conference
; numbers on your system)!
;
; The optional 3rd command-line parm can also contain an extension of
; .QWK - if the BBSID contains the .QWK extension (ie: SOMENET.QWK),
; RJEQWK.EXE will convert this to a .REP file prior to processing.
; Because of this capability, any .QWK file you create/download from
; any other BBS can be imported into Magnum's message databases!
;
; NOTE: The optional 3rd command-line parm is only accepted if the
; ID parm is an account type other than U (user) or M (Magnum Mail).
; You can use the 'outside mail' ID, or create another account type
; to use. This safety measure prevents your users from uploading
; unauthorized REP packets.
;
; >>>>> WARNING <<<<< - You must obtain permission to import messages
; to your BBS from the BBS Sysop who's messages
; you wish to import!
; I'm not up on the legalities, but it may not
; be legal to import messages from Fido, RIME,
; and certain other mail networks.
;
; To run the RJEQWK.EXE program manually, place your .REP (or .QWK) file
; in the WORK DIRectory specified in the STARTUP.n file. Run RJEQWK.EXE
; without any command-line parms for a presentation of the syntax that
; RJEQWK.EXE requires.
;
; -------------- ADD YOUR PARAMETERS BELOW THIS LINE -------------------